home *** CD-ROM | disk | FTP | other *** search
- Path: scoop.eco.twg.com!usenet
- From: mike@jake.eco.twg.com (This space intentionally left blank)
- Newsgroups: alt.computer.consultants,comp.edu,comp.lang.basic.misc,comp.lang.c++,comp.lang.misc,comp.lang.pascal.borland,comp.lang.pascal.delphi.misc,comp.misc,comp.os.msdos.programmer,comp.os.os2.programmer.misc,comp.programming
- Subject: Re: Info on being a Systems Programmer/Analyst?
- Date: 27 Mar 1996 16:47:29 GMT
- Organization: The Wollongong Group
- Message-ID: <4jbrf1$rhh@scoop.eco.twg.com>
- References: <3150eada.14098156@News.why.net> <4j7m18$6d3@shelby.visix.com>
- <4j975b$3sd@scoop.eco.twg.com> <4j9hsv$3so8@news-s01.ny.us.ibm.net>
- <4j9nkh$4qv@nova.dimensional.com> <4jb341$176@fountain.mindlink.net>
- NNTP-Posting-Host: jake.eco.twg.com
-
- In article <4jb341$176@fountain.mindlink.net>, genew@mindlink.bc.ca (Gene Wirchenko) writes:
- >musashi@dimensional.com (Harry Langford) wrote:
- >
- >>tnagy@ibm.net wrote:
- >>: >
- >>: >I'd say that knowing at least two completely different assembly languages
- >>: >well enough to be able write simple programs in them is essential if you
- >>: >want to earn a living as a programmer, even if you never use assembler
- >>: >again.
- >>:
- >>: Finally something we agree on 100%...
- >
- >
- >> Well, I wasn't going to post anything, but now that I
- >> see TWO dubious replies...
- >
- >> Please see header - "Systems Programmer/Analyst".
- >
- >> Having HAD two assembler classes, I can say that in my
- >> current ANALYST position, they are worthless. Set theory,
-
- Yes, an analyst isn't a programmer (though it's possible to be both, you
- apparently are not) and a non-programmer has little use for any programming
- language, assembler or otherwise.
-
- >> algebra, abstract algorithms and just plain business classes
- >> like accounting and economics are more important. By far.
-
- Yep, if you are going to work a problem at the theoretical and problem
- description levels, actual implementation skills are less important.
-
- Of course, understanding implementation is important if you want to be a
- GOOD analyst. Poor analysts tend to invent solutions that are not
- implementable with any kind of efficiency on actual available hardware.
- Knowing something about how the chosen hardware works will limit this a
- great deal and knowing the assembler for it is a good step in that
- direction.
-
- >> Of course, assembly IS important if you're just a coder.
-
- "just a coder"? Lets see an analyst make a penny without a coder in the
- process somewhere. On the other hand, "coders" make money all the time
- without analysts...
-
- > How about finite state automata? FSAs can look a lot like
- >assembler, yet they fit under abstract algorithms.
-
- And they are useful in many situations too.
-
- -- Mike "I've seen them used several times" Bartman --
-
- ==============================================================================
- | I didn't really say all the things that I said. You probably didn't read |
- | what you thought you read. Statistics show that this whole thing is more |
- | than likely just a hideous misunderstanding. |
- ==============================================================================
-
- ==============================================================================
- If any word is improper at the end of a sentence, a linking verb is.
- ------------------------------------------------------------------------------
-
-